jest-config: use UID for default cache folder #3380
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
It appears in some contexts,
os.tmpdir()
doesn't make a difference between different users. As a result, you can run some script that runsjest-runtime
once usingroot
, then later using a non-privileged user; this crashes because that user is unable to write files owned byroot
. Separating by UID helps avoiding permission conflicts on files created by the cache logic.Test plan
Automated testing. Would you suggest a particular test plan for this?